Pro 16 Multimedia System II FAQ
September 1994

The following document contains 70 questions.  These are many of the same
questions that Media Vision technicians answer on a daily basis.  Please be 
aware that this document is approximately 30 printed pages long.

Media Vision is committed to providing  technical support.
Please feel free to contact us via any of the following methods.



Compuserve:	GO MEDIAVISION

BBS:		(510)  770 - 0527
		24 lines
		24 hr. / day
		14.4k baud and downward compatible
		Z - Modem recommended


Tech support 541-882-1177  or 900-555-1133  


If you find it necessary to contact Technical Support, please have 
the following information ready:

Customer ID #__________
The ID # is provided to you during your first call.

Multimedia Product purchased
Date of purchase
Name and version of Multimedia Software installation disk
Type of computer (386, 486, etc.)
Operating system and version (MSDOS, PCDOS, OS/2)
Memory (RAM) installed (2 MB, 4 MB, etc.)

Other devices in your system and their IRQ, DMA, and I/O addresses
if relevant to the problem or call.
Bus mouse
Scanner
Sound Card
CD-ROM drive
Fax/modem
Game card
MIDI device
Video Capture card
Other


1. WHAT ARE VALID DMA CHANNELS?
2. WHAT ARE VALID IRQ CHANNELS?
3. WHAT COMPUTERS WILL THE PRO 16 MULTIMEDIA SYSTEM II
WORK IN?
4. HOW MUCH DISK SPACE IS REQUIRED TO LOAD ALL OF THE FILES 
ONTO THE HARD DRIVE?
5. CAN I HAVE TWO SOUND CARDS IN MY COMPUTER?
6. MY SYSTEM FILES ARE NOT BEING UPDATED AFTER I RUN THE 
INSTALLATION PROGRAM.  HOW DO I FIX THIS?
7. WHAT ARE THE CHANGES THAT ARE MADE TO MY SYSTEM AFTER I 
INSTALL THE SOFTWARE FOR MY SOUND CARD?
8. CAN I USE THE SAME DMA AND IRQ VALUES FOR BOTH THE PRO 
AUDIO SPECTRUM 16 AND SOUND BLASTER EMULATION PORTIONS
OF THE CARD?
9. I'VE HEARD THAT I MIGHT HAVE AUDIO PROBLEMS IF I HAVE A 
SYMPHONY CHIPSET ON MY MOTHERBOARD.  CAN THIS BE 
CORRECTED?
10. IS THE PRO 16 MULTIMEDIA SYSTEM II SUPPORTED UNDER UNIX?
11. WHAT TYPE OF MICROPHONE WILL WORK WITH THE 16 MUTIMEDIA
SYSTEM II?
12. WHAT CAUSES A MEMORY PARITY ERROR?
13. HOW DO I EDIT MY FILES?
14. CAN I LOAD THE MEDIA VISION DEVICE DRIVERS HIGH?
15. WHEN I BOOT MY SYSTEM OR GO INTO WINDOWS, I GET A READ 
ERRORS FROM MY FLOPPY DRIVE.  WHAT IS HAPPENING?
16. WHY AM I GETTING AN "INCORRECT DOS VERSION" ERROR 
MESSAGE?
17. HOW DO I CORRECT A "NOT ENOUGH DRIVER LETTERS" ERROR 
MESSAGE?
18. I'VE INSTALLED THE CARD AND SOFTWARE, BUT I DO NOT GET ANY 
SOUND UNDER DOS OR WINDOWS.  WHAT IS HAPPENING?
19. AFTER I INSTALLED YOUR CARD, MY MODEM STOPPED WORKING.  
IS THIS WHAT IS CALLED AN IRQ CONFLICT?
20. NONE OF MY GAMES WORK WITH SOUND.  WHAT AM I DOING 
WRONG?
21. WHY IS MY AUDIO SO NOISY?
22. HOW DO I SAVE MY VOLUME SETTINGS?
23. WHAT DO I NEED TO DO TO GET MY JOYSTICK TO WORK?
24. WHAT ARE THE PINOUTS FOR THE JOYSTICK/MIDI PORT?
25. DOES THE PRO 16 MULTIMEDIA SYSTEM II SUPPORT DUAL JOYSTICKS?
26. WHAT IS A MIDIMATE?
27. DO YOU OFFER AN UPGRADE POLICY?
28. WHICH JUMPERS ON THE SOUND CARD SHOULD I CHANGE?
29. WHAT DOES THE MVSOUND.SYS STATEMENT DO?
30. HOW DO I CHANGE THE DMA AND IRQ SETTINGS FOR THE PRO 
AUDIO SPECTRUM 16 SECTION OF THE CARD?
31. WHAT ARE ALL OF THE SWITCHES FOR MVSOUND.SYS?
32. WHAT IS THE LATEST VERSION OF MVSOUND.SYS?
33. HOW DO I DISABLE THE SOUND BLASTER COMPATIBILITY MODE?
34. HOW DO I CHANGE THE DMA AND IRQ SETTINGS FOR THE SOUND 
BLASTER SECTION OF THE CARD?
35. WHAT DOES THE SET BLASTER STATEMENT DO?
36. WHAT IS TSLCDR.SYS?
37. WHAT ARE ALL OF THE SWITCHES FOR TSLCDR.SYS?
38. WHAT IS THE MOST CURRENT VERSION OF TSLCDR.SYS?
39. WHICH CD-ROM DRIVES WILL WORK WITH MY CARD?
40. CAN I HAVE MORE THAN ONE SCSI HOST ADAPTER IN MY SYSTEM?
41. DO I NEED TO USE THE SCSI HOST ADAPTER ON THE SOUND CARD 
TO OPERATE MY CD-ROM DRIVE?
42. I JUST INSTALLED A SCSI CD-ROM DRIVE THAT IS SUPPOSED TO 
WORK WITH YOUR CARD, BUT THE DRIVE ISN'T WORKING.  WHAT DO 
I DO?
43. WHAT DOES THE MSCDEX.EXE STATEMENT DO?
44. WHY DOES MY SYSTEM HANG WHEN IT TRIES TO LOAD 
MSCDEX.EXE?
45. I AM GETTING CDR 101 ERRORS.  WHAT CAN I DO TO FIX THIS?
46. I'M GETTING A "NO SCSI HOST ADAPTER DETECTED" ERROR 
MESSAGE.  HOW DO I FIX THIS?
47. MY THIRD PARTY CD-ROM DRIVE IS NOT WORKING.  WHAT GIVES?
48. HOW DO I GET CD AUDIO FROM MY THIRD PARTY CD-ROM DRIVE?
49. HOW DO I INCREASE THE PERFORMANCE OF MY CD-ROM DRIVE?
50. WHAT WILL DECREASE THE PERFORMANCE OF MY CD-ROM 
DRIVE?
51. WHAT IS WAVETABLE SYNTHESIS?
52. IS MY CARD WAVETABLE UPGRADEABLE?
53. WHAT IS THE KORG WAVETABLE UPGRADE?  WILL IT WORK ON 
MY SYSTEM?
54. WHAT ARE THE FEATURES OF THE KORG WAVETABLE UPGRADE 
CARD?
55. I AM GETTING "ADLIB IS ALREADY IN USE" ERRORS WHEN I TRY TO 
RUN MY DOS APPLICATIONS THROUGH WINDOWS.  HOW DO I GET RID 
OF THIS ERROR MESSAGE?
56. I AM GETTING THE FOLLOWING ERROR MESSAGE, "CAN'T FIND 
VER. 2.00 OF VDMAD.386."
57. WHY IS WINDOWS MAKING THIS ANNOYING LOOPING SOUND 
WHEN WINDOWS FIRST STARTS?
58. I AM GETTING AN ERROR MESSAGE STATING THAT I NEED TO 
"LOAD MULTIMEDIA EXTENSIONS" BEFORE I RUN THE INSTALLATION 
PROGRAM.  HOW DO GET RID OF THIS MESSAGE?
59. MIDI DOESN'T WORK ON MY SYSTEM.  HOW DO I CONFIGURE THE 
MIDIMAPPER?
60. EVER SINCE I INSTALLED YOUR CARD, WINDOWS LOCKS UP WHEN I 
TRY TO EXIT.  WHAT IS HAPPENING?
61. I AM GETTING THE ERROR MESSAGE "CAN NOT SUCCESSFULLY 
REGISTER THE SERVER" WHEN ATTEMPTING TO ACCESS ANY OF THE 
POCKET TOOLS IN WINDOWS. HOW DO I CORRECT THIS PROBLEM?
62. WHY DO ALL OF  MY SOUNDS PLAY FAST?  IT SOUNDS LIKE MY 
CARD IS CHIPMUNKING.
63. POCKET CD WON'T WORK.  I AM GETTING THE FOLLOWING ERROR 
MESSAGE.  "THERE IS AN UNDETECTABLE PROBLEM IN LOADING THE 
SPECIFIED DEVICE DRIVER."
64. I AM UNABLE TO USE THE MEDIA PLAYER IN WINDOWS TO PLAY 
AUDIO CDS.  HOW CAN I CORRECT THIS PROBLEM?
65. I AM ONLY GETTING SOUND FROM ONE CHANNEL WHEN PLAYING 
A MUSIC CD.
66. IS THERE AN SOFTWARE DEVELOPER'S KIT AVAILABLE FOR THE 
PRO 16 MULTIMEDIA SYSTEM II?
67. HOW DO I GET TBPRO TO WORK?  IT USED TO WORK FINE, BUT IT 
DOESN'T WORK ANYMORE.
68. CAN I CONNECT OTHER SCSI DEVICES TO THE PRO 16 MULTIMEDIA
SYSTEM II?
69. I AM GETTING THE FOLLOWING ERROR MESSAGE WHEN I USE 
RECFILE.  "FILE IS FULL OR BLOCKED."I AM ALSO NOT ABLE TO 
RECORD 16 BIT FILES.  WHAT IS HAPPENING HERE?
70. WHY AM I GETTING A GPF (GENERAL PROTECTION FAULT) IN 
"USER.EXE" WHEN I TRY TO USE POCKET RECORDER?

1. What are valid DMA channels?

CHANNEL			USAGE
8 BIT CHANNELS:
0			MEMORY REFRESH
1			SDLC
2			FLOPPY DISK
3			UNASSIGNED

16 BIT CHANNELS, AT ONLY:
4			UNASSIGNED
5			UNASSIGNED
6			UNASSIGNED
7			UNASSIGNED

2. What are valid IRQ channels?
INT#			Description
NMI			PARITY *
IRQ "0"			TIMER *
IRQ "1"			KEYBOARD *
IRQ "2"			RESERVED(XT), CASCADE
IRQ "3"			COM or SDLC
IRQ "4"			COM or SDLC
IRQ "5"			HARD DISK(XT), LPT2-AT
IRQ "6"			FLOPPY DISK
IRQ "7"			LPT 1

HIGH ORDER INTERRUPTS
IRQ "8"			REAL-TIME CLOCK
IRQ "9"			CASCADE
IRQ "10"		UNASSIGNED
IRQ "11"		UNASSIGNED
IRQ "12"		UNASSIGNED
IRQ "13"		80287 COPROCESSOR
IRQ "14"		HARD DISK
IRQ "15"		UNASSIGNED

* These interrupts exist on the system board and are not available on the 
bus connector.

3. What computers will the Pro 16 Multimedia System II work in?
The Pro 16 Multimedia System II was designed around the IBM AT 
specification.  It will work in a 486/50 if the bus (I/O CLK) speed is 
lowered down to 8 Mhz.  Please note that the bus speed is not the 
same as the CPU speed.  The minimum requirements would be a 386 
or higher processor.

4. How much disk space is required to load all of the files 
onto the hard drive?
About 10 megs for the Pro 16 Multimedia System II.

5. Can I have two sound cards in my computer?
No.  Other than specialized software that would be developed by an end 
user, there are currently no applications that will utilize more than one 
sound card at a time.  Please note that the only exception to this rule is if 
you are installing a wavetable upgrade card that was designed to enhance 
your current sound card.


6. My system files are not being updated after I run the installation program.
How do I fix this?
1.) At the DOS prompt, type:

SETVER C:\DOS INSTALL.EXE 6.00   [enter]

DOS will issue a long warning message about compatibility, and you may 
want to read it.

2.) REBOOT THE SYSTEM!  The change will NOT take effect until the 
system is restarted!

3.) Re-install your Media Vision software from floppy disk.  The 
installation  should now work.

4.)  Remove INSTALL.EXE from the SETVER list with the following 
command:

SETVER C:\DOS INSTALL.EXE /D   [enter]

Alternately, the computer could be booted from a DOS 5.0 or DOS 6.0 
bootable  diskette.

7. What are the changes that are made to my system 
after I install the software for my sound card?
Here are the changes that are made to your system files.

CONFIG.SYS

DEVICE=C:\PRO16MM2\MVSOUND.SYS D:5 Q:7 S:1,220,1,5 M:0 J:1
DEVICE=C:\PRO16MM2\TSLCDR.SYS /D:MVCD001 /W3

(Note:  If your computer uses a Phoenix or Award Bios, please add the 
following parameter to the end of the MVSOUND.SYS line:  "/W:0" )

AUTOEXEC.BAT

SET BLASTER=A220 I5 D1 T3
C:\PRO16MM2\MSCDEX.EXE /D:MVCD001 /M:10  /V

SYSTEM.INI

[386Enh]
device=vpasd.386
dmabuffersize=064

[mci]
CDAudio=mcicda.drv
mixer=mcimixer.drv

[drivers]
mixer=mvmixer.drv
timer=timer.drv
midimapper=midimap.drv
wave=mvproaud.drv
aux=mvproaud.drv
midi=opl3.drv
midi1=mvproaud.drv

[Multimedia.Setup]
audio=mvproaud.drv,0,0,0

[mvproaud.drv]
dma=5
irq=11

[opl3.drv]
drumchannel=10

8. Can I use the same DMA and IRQ values for both the Pro Audio Spectrum 
16 and Sound Blaster emulation portions of the card?
You CANNOT use the same DMA and IRQ for the Pro 16 Multimedia System
II and Sound Blaster emulation portions of the board.  The values MUST be 
different.

9. I've heard that I might have audio problems if I have a Symphony chipset 
on my motherboard.  Can this be corrected?
Yes.  You need to download SYMPFIX.EXE from the Media Vision BBS.  
Please follow the directions in the included text file.  If you have a 
Symphony chipset and you are not experiencing any sound problems, then 
you do not need the SYMPFIX patch.  Here is the DEBUG routine used in 
the SYMPFIX patch.  

DEBUG 			[enter]
O A8 05			[enter]
O A9 60 		[enter]
Q 			[enter]

10. Is the Pro 16 Multimedia System II supported under UNIX?
Unfortunately, there is no support for the Pro 16 Multimedia System
II under UNIX.

11. What type of microphone will work with the Pro 16 Multimedia System II?
The Pro 16 Multimedia System II accepts dynamic microphones with impedance of 
600 to 20K Ohms.

12. What causes a Memory Parity error?
This is typically caused by a DMA conflict.  You will find the DMA 
parameter on the MVSOUND.SYS line in the CONFIG.SYS file.  The 
DMA is set with the D:x parameter.  Many times increasing the 
DMABUFFERSIZE in the [386Enh] section of the SYSTEM.INI file will 
resolve this problem.  Here is a sample line.

DMABUFFERSIZE=128

13. How do I edit my files?
You can use Notepad in Windows to edit your files.  You can also use the 
EDIT command under DOS.  You can also use the SYSEDIT program in 
Windows.  To use the SYSEDIT program in Windows:
1.)  Ensure that you are at your Program Manger.
2.)  Click on FILE under Program Manager.
3.)  Click on RUN
4.)  Enter the following on the command line:
SYSEDIT  [enter]
5.)  Edit the file.  When you are ready to save the file, click on FILE and 
then SAVE.
6.)  Click on FILE and then EXIT to exit the editor.

To use the EDIT program under DOS:

1.)  Enter the following at the DOS prompt:
CD\  [enter]
2.) Enter the following at the prompt:
EDIT  CONFIG.SYS  [enter]
3.)  Edit the file.  When you are ready to save the file, hold down [ALT] + 
[F].  Then, press [X] to exit.  You will be prompted to save the file.  When 
prompted to save the file, press [Y].

14. Can I load the Media Vision device drivers high?
Yes.  The Media Vision device drivers can be loaded into upper memory.  
Here is a sample line which loads MVSOUND.SYS into upper memory.

DEVICEHIGH=C:\PRO16MM2\MVSOUND.SYS D:3 Q:7 S:1,220,1,5 M:0 J:1

Here is sample line that loads MSCDEX.EXE into upper memory.

LH  C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10

15. When I boot my system or go into Windows, I get  
read errors from my floppy drive.  What is happening?
Check your CONFIG.SYS and AUTOEXEC.BAT files for references to 
your floppy drives.  Unless you typically boot from your flopyy drive, none 
of your lines should try to load drivers or TSRs from the a floppy drive.  
Check the PATH statement in your AUTOEXEC.BAT file.  It is likely that 
you will find some reference to your floppy drive on this line.

16. Why am I getting an "Incorrect DOS Version" error message?
This error message is coming from the MSCDEX.EXE line in the 
AUTOEXEC.BAT file.  MSCDEX.EXE is a TSR that is used in 
conjunction with a  CD-ROM drive.  

NOTE:  If you do not have a CD-ROM drive, you can delete this line from 
your AUTOEXEC.BAT file.  You can also delete the CD-ROM driver line 
in your CONFIG.SYS file.  

MSCDEX stands for Microsoft CD Extensions.  MSCDEX is a DOS 
version sensitive program. If you do have a CD-ROM drive, then here are 
the steps that you would take to resolve the problem.

1.)  Use the MSCDEX.EXE from the DOS directory.   Here is a sample 
line.

C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10

If you are using DOS 5.00, the version that MSCDEX.EXE should report 
is 2.21.
If you are using DOS 6.00, the version that MSCDEX.EXE should report 
is 2.22.
If you are using DOS 6.20, the version that MSCDEX.EXE should report 
is 2.23.

2.)  Assign the drive letter to the CD-ROM drive (on the MSCDEX line in 
the AUTOEXEC.BAT) with the /L:$  parameter.  Here is a sample line.

C:\DOS\MSCDEX.EXE /D:MVCD001 /M:10 /V /L:D

where $ is the drive letter for the CD-ROM drive.  In our example, the CD-
ROM drive is going to be drive D.

3.)  Make sure you have a LASTDRIVE statement in your CONFIG.SYS 
file:

LASTDRIVE=E

Where $ is at least one drive letter BEYOND the last physical drive on the 
system.  Again, in our example  the CD-ROM drive letter is D.

17. How do I correct a "not enough driver letters" error message?
You will want to make the following changes to correct this error.

1.)  Assign the drive letter to the CD-ROM drive (on the MSCDEX line in 
the AUTOEXEC.BAT) with the /L:$  parameter.  Here is a sample line.

C:\DOS\MSCDEX.EXE /D:MVCD001 /M:10 /V /L:D

where $ is the drive letter for the CD-ROM drive.  In our example, the CD-
ROM drive is going to be drive D.

2.)  Make sure you have a LASTDRIVE statement in your CONFIG.SYS 
file:

LASTDRIVE=E

Where $ is at least one drive letter BEYOND the last physical drive on the 
system.  Again, in our example  the CD-ROM drive letter is D.


18. I've installed the card and software, but I do not get any sound under DOS
or Windows.  What is happening?
Here are some suggestions that should help you sort out what is happening 
on your system.  The first thing you want to do is to make sure that the 
sound card is functioning under DOS.

Here is a sample configuration for your CONFIG.SYS file.

DEVICE=C:\PRO16MM2\MVSOUND.SYS D:5 Q:10 S:1,220,1,5 M:0 J:1 T:1 /W:0

Reboot the system.  Make sure that your speakers or headphones are 
plugged into the OUT jack on the back of the sound card.  Change 
directories to the Media Vision directory (PRO16MM2).  Test the sound by 
entering the following line:  Please note that you may use something other 
than the TEST.WAV file to test your sound.

PAS  RESET			[enter]
PLAYFILE  TEST.WAV		[enter]

You should hear the .WAV file play.  If you hear no sound, then enter the 
following at the DOS prompt:

DEBUG 				[enter]
O A8 05				[enter]
O A9 60 			[enter]
Q 				[enter]

Try the PLAYFILE command again.  If this now works, download 
SYMPFIX.EXE from the Media Vision BBS, and follow the directions in 
the included text file.

If this does not work, try a different DMA / IRQ combination.  Once there  
is sound in DOS, Windows should also have sound.  If you still have no 
sound  in Windows, then check to make sure that the DMA and IRQ 
settings match the D: and Q: parameters on the MVSOUND line.

You should also try the card in a different slot.  Make sure that the BUS 
speed on your system is set to 8.33 mhz.

19. After I installed your card, my modem stopped working.  Is this what is
called an IRQ conflict?
Yes, this is an IRQ conflict.  It is likely that you are using IRQ 3 for your 
sound card as well as your modem.  You will need to stop using IRQ 3 for 
the sound card.  Here are some steps to assist you in finding a suitable 
IRQ.

Please make the following changes to your system files.

CONFIG.SYS

DEVICEHIGH=C:\PRO16MM2\MVSOUND.SYS D:3 Q:10 S:1,220,1,7 M:0 J:1

Make sure that these are the last two lines in your CONFIG.SYS file.

AUTOEXEC.BAT

SET  BLASTER=A220  I7  D1  T3

Test the DMA and IRQ settings by using PLAYFILE under DOS.

Use PLAYFILE under DOS to make sure that we are using a solid DMA 
channel. Make sure that your speakers or headphones are  plugged into the 
OUT jack on the back of the sound card.  Change directories to the Media 
Vision directory (PRO16MM2). Test the sound by entering the following 
line:  Please note that you may use something other than the TEST.WAV 
file to test your sound.


C:\PRO16MM2>PLAYFILE  TEST.WAV	 [enter]

You should hear the .WAV file play once.

If this does not sound normal, adjust the IRQ setting on the 
MVSOUND.SYS line in your CONFIG.SYS file.  Here is a sample line for 
your system.  Once you have sound under DOS, the Windows sound 
should follow.  Make sure that you are using the same DMA and IRQ 
settings under DOS and Windows.  The DMA and IRQ settings for 
Windows can be found in the [mvproaud.drv] section near the bottom of 
the SYSTEM.INI file.

20. None of my games work with sound.  What am I doing wrong?
The lack of sound is probably related to insufficient conventional memory 
for the program.

Consult your DOS manual regarding memory management.  The Media 
Vision drivers can load into upper memory without any problems. It is 
recommended that your conventional memory be at least 590 kb.  This 
should be adequate to run most applications.

If enough memory cannot be made available, you may need to create a 
boot disk, with a minimal number of drivers.

Finally, please refer to your instruction manual that came with the game.  
You may also find it helpful to contact the game manufacturer.

21. Why is my audio so noisy?
When used in computers having certain combinations of hardware 
(processor, BIOS, and chipset), the Pro Audio Spectrum sound cards can 
produce static, popping, and hiss.  There are several solutions available to 
you.

First, try adding a T:1 as well as a /W:0 to the end of the MVSOUND line 
in the CONFIG.SYS.  For example:

DEVICE=C:\PRO16MM2\MVSOUND.SYS D:3 Q:7 S:1,220,1,5 M:0 J:1 T:1 /W:0

Restart your computer, and see if the noise goes away.  If not, try adjusting 
your DMA settings.  You may want to switch to  16 bit DMA IRQ settings 
if you are currently using 8 bit DMA and IRQ settings.  If you are currently 
using  16 bit DMA and IRQ settings,  try dropping down to 8 bit DMA and 
IRQ settings.  It is recommended that you use the same DMA and IRQ 
setting for both DOS and Windows.  The DMA setting for Windows can 
be found near the bottom of the SYSTEM.INI file in the 
[MVPROAUD.DRV] section.  It is likely that the DMA change and the 
addition of the T:1 will eliminate the popping and static noise.  

You may also want to investigate your mixer settings.  Make sure that you 
do not have something turned up too much.  You can check the mixer 
settings by using the PAS utility under DOS.  If  you would like to reset 
the DOS mixer, you can type the following at a DOS prompt:

PAS RESET  [enter]

At the DOS prompt, type PAS *   [enter].   Under Windows use the 
Pocket Mixer to check your settings.

22. How do I save my volume settings?
Volume settings for the Pro 16 Multimedia System II can be initialized
when the computer starts up.  Here's how:

1) At the DOS prompt, type

PAS *  [enter]

2) Adjust the volume settings to the desired levels.

3) Hold down <SHIFT> and press the function key F5.  This saves the 
mixer settings under the F5 setting.  To test the procedure, press the F4 
key.  This will reset the mixer to the default volume levels.  Press the F5 
key, and your saved volume settings should be recalled.

4) Press the ESC key to exit the mixer.

5) Edit your AUTOEXEC.BAT file.

6) Check to see that the Media Vision directory is in the PATH statement.  
Add it if it isn't.

7) Add a new line UNDERNEATH your PATH statement:

PAS F5  (Note: you may also use: PAS SET F5)

8) Save the changes to the AUTOEXEC.BAT.  Reboot.  Your new volume 
levels should be automatically set every time you start the computer.

23. What do I need to do to get my joystick to work?
You need to turn the Joystick port "on" on the MVSOUND.SYS line.  
You will use the "J:x" parameter to do this.  Here is a sample line that has 
the game port turned "on."

DEVICE=C:\PRO16MM2\MVSOUND.SYS  D:3  Q:7  S:1,220,1,5  M:0 J:1

Here are some other tips that should ensure that your joystick port works.

1.)  Make sure that you have only 1 active game port on your system.  
Some motherboards have a built in game port.  You will need to disable the 
built in game port to use the game port on the sound card.  It does not 
matter which game port you use.   So, if you are unable to disable a game 
port already on the system, just disable the game port on the sound card.

"J:1" turns the joystick on.
"J:0" turns the joystick off.

2.)  Try turning the TURBO switch off on your PC.  

3.)  Try putting the card in a different slot.

4.)  Make sure that the BUS speed on your system is set to 8 mhz.

Some Hard drive controllers and motherboards may have a joystick port 
built into them.

Remove the sound card and connect the joystick to the Multi I/O card 
game port.  If it works the game port is NOT disabled.

Sometimes you will not be able to find the actual port that you would plug 
the Joystick into, however the interface may still be there and enabled!  
Look on all cards (including the mother board) for 16 pin header 
connectors with nothing plugged into them.  It is possible that this is a 
header connector for a joystick interface. 

Finally, you may need to reinstall your game to get the joystick recognized 
by the software.

24. What are the pinouts for the Joystick/Midi port?

1	+5VDC
2	JOYSTICK 1 FIRE 1
3	JOYSTICK 1 X
4	GROUND
5	GROUND
6	JOYSTICK 1 Y
7	JOYSTICK 1 FIRE 2
8	+5VDC
9	+5VDC
10	JOYSTICK 2 FIRE 1
11	JOYSTICK 2 X
12	MIDI OUT  (GROUND on MIDI Mate)
13 	JOYSTICK 2 Y
14	JOYSTICK 2 FIRE 2
15	MIDI IN (+5VDC on MIDI Mate)

25. Does the Pro 16 Multimedia System II support dual joysticks?
The Pro 16 Multimedia System II will not support dual joysticks in its current 
configuration.  Here are the pinouts to create a modified joystick to 
support a dual joystick.

D15S (male)----------D15S(female)
to PAS-----------------to joystick
1------------------------1
2------------------------2
3------------------------3
4------------------------4
5--------------------x---5
6---------------------|---6
7---------------------|---7
8---------------------|---8
9 -----x--------------|---9
10----|.............. |--10
11----|.............. |--11
12----|.................12
13----|------------------13
14----|------------------14
15....|-----------------15

(........) = no connection

If you have a Midimate, the Midimate joystick port will support dual 
joysticks.

26. What is a Midimate?
A Midimate is a device that will allow you to connect a music keyboard to 
your sound card.  The Midimate connects to the joystick/midi connector 
and your music keyboard.

27. Do you offer an upgrade policy?
Media Vision does not currently have an upgrade program.

28. Which jumpers on the sound card should I change?
None.

29. What does the MVSOUND.SYS statement do?
It initializes and enables the Pro 16 Multimedia System II to produce 
sound under DOS.

30. How do I change the DMA and IRQ settings for Pro 16 Multimedia 
System II section of the card?
The DMA and IRQ settings for the sound card are software controllable.  
You will need to modify the D:# and Q:# parameters on the 
MVSOUND.SYS line in your CONFIG.SYS file. Please see "What are all 
of the switches for MVSOUND.SYS?" for even more information 
regarding the D:# and Q:#  parameters.  Here is a sample 
MVSOUND.SYS line.  In this example, the DMA will be 3 and the IRQ 
will be 7.

DEVICE=C:\PRO16MM2\MVSOUND.SYS D:3  Q:7  S:1,220,1,5 M:0 J:1

31. What are all of the switches for MVSOUND.SYS?
Options:
D:#	# = PAS DMA Channel		(default: 3)
Q:#	# = PAS IRQ Channel		(default: 7)
S:#	# = SB on/off,port,dma,irq	(default: 1,220,1,5)
M:#	# = MPU on/off,port,irq		(default: 0,330,2)
J:#	# = Joystick status, 1=on-0=off (default: 1)
V:#	# = Volume Level, 0-100 (%)	(default: 80)
T:#	# = Clock Source, 0(CPU)/1(PAS) (default: 0)
/W:#	Allow Warm Boot, 1(on) or 0(off)(default: 1)
G	Increase Gain			(default: off)
X	display PAS configuration found
U	Unload driver after configuration

32. What is the latest version of MVSOUND.SYS?
As of September 1994, the latest version of MVSOUND.SYS is 3.24.  The 
file is available on the BBS or Compuserve as MVSND324.EXE

33. How do I disable the Sound Blaster compatibility mode?
You will need to modify the MVSOUND.SYS line in your CONFIG.SYS 
file.  Here is a sample line with Sound Blaster emulation disabled.  Use the 
S:# parameter to enable or disable the Sound Blaster emulation.  Please see 
"What are all of the switches for MVSOUND.SYS?" for even more 
information regarding the S:# parameter.

DEVICE=C:\PRO16MM2\MVSOUND.SYS D:3 Q:7 S:0 M:0 J:1

34. How do I change the DMA and IRQ settings for the Sound Blaster section 
of the card?
You will need to modify the MVSOUND.SYS line in your CONFIG.SYS 
file. Use the S: parameter to configure the Sound Blaster emulation.  Here 
is a sample line with Sound Blaster emulation enabled using DMA 1, IRQ 
5, and I/O ADDRESS 220.  Remember that you must also modify the SET 
BLASTER statement in the AUTOEXEC.BAT file as well.

CONFIG.SYS

DEVICE=C:\PRO16MM2\MVSOUND.SYS  D:3  D:7  S:1,220,1,5  M:0 J:1

(Note: S:# = SB on/off,port,dma,irq)

AUTOEXEC.BAT

SET BLASTER=A220  D1  I5  T3

(Note: A=PORT  D=DMA  I=IRQ  T=Sound Blaster emulation mode)

35. What does the SET BLASTER statement do?
The SET BLASTER statement sets environment variables for the Sound 
Blaster emulation on your card that many multimedia applications need to 
function properly.

36. What is TSLCDR.SYS?
TSLCDR.SYS is the device driver for SCSI CD-ROM drives that use the 
Pro 16 Multimedia System II as a SCSI host adapter.  It was written by 
Trantor for Media Vision.  Media Vision does all of the support for this driver.

37. What are all of the switches for TSLCDR.SYS?
Syntax:

DEVICE=C:\PRO16MM2\TSLCDR.SYS /D:MVCD001 /R /P3 /W0

/D:MVCD001  is the logical device name.  This needs to match logical 
device name used on the MSCDEX.EXE line in the AUTOEXEC.BAT file.

/R	Reset SCSI bus on CPU reset

/P#	0 Disables seek and prefetch modes
	1 Enables seek mode
	2 Enables prefetch mode
	3 Enables both seek and prefetch modes
	(Note there is no colon here!)

/W#	0 Do not pause
	2 Pause if SCSI device detected
	3 Pause if no SCSI device detected

38. What is the most current version of TSLCDR.SYS?
As of September 1994, the current version of TSLCDR.SYS is 3.16, but 
some CD-ROM drives require a special version 3.12 TSLCDR.SYS.

39. Which CD-ROM drives will work with my card?
CD-ROM DRIVES SUPPORT LIST
REV. July 15, 1994

INTERNAL SCSI CD-ROM DRIVES
Chinon			CDS-431[#6], CDS-435[#4], CDS-535[#1]
Hitachi			CDR-3650 (with rev. 0008 ROM or later), 
			CDR-3750[#3]
NEC			CDR-55JD[#2], CDR-80[#5], CDR-82, CDR-
			83[#3], 
			CDR-83J[#3],CDR-83M[#3], CDR-84[#3], 
			CDR-84J[#3],
			CDR-84-1[#2], CDR-500[#2] 
Philips			CM-425A[#1] 
Sanyo			CDR H93MV [req. TSLCDR.SYS ver.3.12]
Sony			CDU-541[#3], CDU-561[#2], CDU-561-31[#1] 
Teac			CD-50[#1] (Firmware Rev. 1.00 only)
Texel			DM-3020, DM-302[#1], DM-3024[#2], DM-
			3028[#1] 
Toshiba			XM-3201B[#3], XM-3401B[#2]

EXTERNAL SCSI CD-ROM DRIVES
Apple			CD-SC (Sony CDU-8001), CD-SC Plus (Sony 
			CDU-8002), 
			CD-300 (Sony CDU-8003)[#1]
CD Technologies	Porta-Drive
Chinon			CDC-431[#6], CDX-431[#6], CDC-435[#3], CDX-
			435[#3], CDX-535[#1] 
Denon			DRD-253
Hitachi			CDR-1553S, CDR-1650, CDR-1750S[#3] 
IBM			3510
Laser Magnetics		CM-212, CM-214, CM-231[#3]
NEC			CDR-25[#3], CDR-25BJ[#3], CDR-35[#5], 
			CDR-36, 
			CDR-36M[#3], CDR-37[#3], CDR-38[#2], 
			CDR-72, 
			CDR-73[#3],CDR-73M[#3], CDR-74[#3], 
			CDR-74-1[#2], 
			CDR-77[#5], CDR-400[#2], CDR-600[#2] 
Panasonic		CR-501-S[#6] (Firmware Rev. 1.0b or later)
Pioneer			DRM-600[#3] (6 disk changer)
Sony			CDU- 6110[#3], CDU-6111[#3], CDU-6211[#3], 
			CDU-7211[#3]
Sun			Sony CDU-8012[#1]  (Photo CD Single Session 
ONLY)
Texel			DM- 3010, DM-3120, DM-5010, DM-5020, DM-
			502[#1], DM-5022, DM-5024[#2], DM-5028[#1],
			DM-5110, DM-5120, DM-7120A, DM-7120B
Toshiba			XM-3100, XM-3101, XM-3201A[#3], XM-	3301[#3], 
			XM-3301TA[#2], XM-3401P or E[#2], XM-5100A
Notes:
[#1]    Requires TSLCDR.SYS version 3.07a.
[#2]    Will support Photo CD Multi Session when using the 
TSLCDR.SYS v. 3.02 or later.
[#3]    Will support Photo CD Single Session when using the 
TSLCDR.SYS driver v.1.46F or later.
[#4]    Requires TSLCDR.SYS Version 3.02, and supports Photo CD 
Single Session.
[#5]    TSLCDR.SYS v.1.46 or later will not support these CD-ROM 
drives because of the hardware differences with Photo CD compatibly, however 
version 1.44 will support them.  Please contact Customer Service and 
request TSLCDR.SYS Ver. 1.44 (Requires PAS16 or older sound card).
[#6]    Known not to support photo CD.

Not all CD-ROMs support CD audio (redbook).  Some CD_ROMs are 
data only, check with the manufacturer of the drive.  Chinon CDS-431 may 
require a 40 to 50 pin converter, contact Chinon at (310)533-0274 to 
obtain it. If the CD ROM drive is not on the list, and it supports the SCSI 2 
command set, then driver version 3.07a may support it. 

ADDITIONAL INFORMATION:
Cables for most of the SCSI CD-ROM drives listed above are available 
from any dealer that sells Multimedia supplies.  For a referal, please contact 
Customer Service.  To obtain SCSI or ASPI drivers for other types of 
SCSI devices (optical drives, hard disks, removable drives, etc.), contact 
Adaptec at 1-408-945-8600 and ask for "Pre-Sales".  Get the product 
called SCSIworks! by Trantor.

40. Can I have more than one SCSI host adapter in my system?
Yes.  You can have as many SCSI host adapters in the same system 
as there are available slots.  The Pro 16 Multimedia System II's SCSI will 
not interfere with other SCSI adapters.  The only possible conflicts would 
be with DMA's, IRQ's, or I/O ports used by another card.

41. Do I need to use the SCSI host adapter on the sound 
card to operate my CD-ROM drive?
No.  The only connection that you will need to make is a CD-Audio 
connection.  You would only need to make this connection if you plan on 
using the mixer on the sound card to control CD-Audio.  You can purchase 
an Audio cable for your CD-ROM drive and sound card from TTS. The 
telephone and fax numbers for TTS are:

Voice	800 - 887 - 4968
Voice	408 - 982 - 0653
FAX	408 - 982 - 0738

42. I just installed a SCSI CD-ROM drive that is supposed to work with your 
card, but the drive isn't working.  What do I do?
Here are some troubleshooting tips that should get your drive operational.

Make sure that you are using the proper version of TSLCDR.SYS for your 
CD-ROM drive.

Make sure you have a LASTDRIVE statement in your CONFIG.SYS file:

LASTDRIVE=$

Where $ is at least one drive letter BEYOND the last physical drive on the 
system.

Try the following sample lines in place of your current lines in the 
CONFIG.SYS file.

DEVICE=C:\PRO16MM2\MVSOUND.SYS D:5 Q:11 S:1,220,1,5 M:0 J:1 /W:0
DEVICE=C:\PRO16MM2\TSLCDR.SYS /D:MVCD001 /R

Make sure that these are the last two lines in your CONFIG.SYS file.

You will also want to make sure that you are using the latest version of 
MSCDEX.EXE on your system.  Here is a sample line for your 
AUTOEXEC.BAT file that will ensure that you are using the proper 
version of MSCDEX.EXE for you system.  Make sure that the 
MSCDEX.EXE line in the AUTOEXEC.BAT file is at the TOP of the file.    
Also, assign the drive letter to the CD-ROM drive with the /L: parameter.

C:\DOS\MSCDEX.EXE /D:MVCD001 /M:10 /V /L:$

Where $ is the drive letter for the CD-ROM drive.  

If you are using DOS 5.00, the version that MSCDEX.EXE should report 
is 2.21.
If you are using DOS 6.00, the version that MSCDEX.EXE should report 
is 2.22.
If you are using DOS 6.20, the version that MSCDEX.EXE should report 
is 2.23.

43. What does the MSCDEX.EXE statement do?
MSCDEX.EXE is a TSR that is used in conjunction with a  CD-ROM 
driver.  MSCDEX stands for Microsoft CD Extensions.  MSCDEX is a 
DOS version sensitive program.  Here is a sample line for your 
AUTOEXEC.BAT file that will ensure that you are using the proper 
version of MSCDEX.EXE for your system.

C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10

If you are using DOS 5.00, the version that MSCDEX.EXE should report 
is 2.21.
If you are using DOS 6.00, the version that MSCDEX.EXE should report 
is 2.22.
If you are using DOS 6.20, the version that MSCDEX.EXE should report 
is 2.23.

44. Why does my system hang when it tries to load MSCDEX.EXE?
Make sure that you are loading MVSOUND.SYS before TSLCDR.SYS.
You also want to make sure that the "name" of the CD-ROM drive 
matches on the TSLCDR.SYS and MSCDEX.EXE lines.  The "name" of 
the drive should be:

MVCD001

Run MSD to find out what TSLCDR.SYS is using for a "name" for the 
CD-ROM drive.  Sometimes TSLCDR.SYS will ignore the "name" that is 
specified on the TSLCDR.SYS line in the CONFIG.SYS file.  MSD will 
tell us what it really using.

When in MSD, look at the DEVICE DRIVERS section.  In the DEVICE 
DRIVERS section you will see several headings at the top of the screen.  
The first heading will be DEVICE, and the second heading will be 
FILENAME. 

Find TSLCDR under the FILENAME heading.   You will then see the 
"name" over to the right of TSLCDR (under the DEVICE column) that 
TSLCDR.SYS is using for the CD-ROM.  If the "name" is something other 
than "MVCD001", then use whatever TSLCDR.SYS wants to use.  

Remember to use this "name" on the TSLCDR.SYS line and the 
MSCDEX.EXE line.

You might also try the following sample lines in place of your current lines 
in the CONFIG.SYS file.

DEVICE=C:\PRO16MM2\MVSOUND.SYS D:5 Q:11 S:1,220,1,5 M:0 J:1 /W:0
DEVICE=C:\PRO16MM2\TSLCDR.SYS /D:MVCD001 /R

Make sure that the MSCDEX.EXE line in the AUTOEXEC.BAT file is at 
the TOP of the file.  Here is a sample line:

C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10

45. I am getting CDR 101 errors. What can I do to fix this?
Troubleshoot  your CD-ROM drive while in DOS. A CDR 101 error is a 
very difficult error to troubleshoot via FAQ.  Here are all of the possible 
trouble shooting tips that will either eliminate the problem, or at least 
narrow it down.  The PC is assuming that the driver is loaded properly, but 
the CD-ROM drive is having problems reading the disk.  Please try the 
following.

1.) Make sure that you are not trying to read an audio disc.

2.)  Check the internal flat ribbon cable.  Disconnect and reconnect the 
ribbon cable that connect the CD-ROM drive to the sound card.  Do this at 
both ends of the cable.  Try a different or new ribbon cable.  It is possible 
that the cable is bad.  If the cable is correctly connected to the card, it is 
possible that it is plugged in backwards on the CD-ROM drive.  In most 
cases the drive's connector is "keyed" so the cable cannot be put on wrong, 
however, it is possible to force the cable on incorrectly.  Check the cable 
for damage, kinks, or being stretched to the maximum length.  Make sure 
the ribbon cable is installed with the colored edge up (toward the 4 pin 
connector, J4) and is seated completely.  When you re-install the cable, 
check for bent pins; also, check the cable to make sure that it is not off-set 
where it is not covering all of the pins.

3.)  Make sure there is a LASTDRIVE statement in the CONFIG.SYS and 
that it is high enough to cover the CD-ROM drive plus one drive.  In other 
words, if the CD-ROM drive is drive E, then the statement should read as 
follows:

LASTDRIVE=F

This is a requirement of MSCDEX.EXE.  You don't need a LASTDRIVE 
statement if the CD-ROM drive is drive D.

4.)  The CD-ROM driver should ideally be located at the bottom of the 
CONFIG.SYS file.  Very rarely should it be at the top of the file.  If the 
CD-ROM driver loads first, it's possible to cause other problems.  As a 
test, move MVSOUND.SYS  and the CD-ROM driver to the top of the 
CONFIG.SYS file.  Make sure that you are using the latest version of 
MSCDEX.EXE on your system.  Here is a sample line for your 
AUTOEXEC.BAT file that will ensure that you are using the proper 
version of MSCDEX.EXE for you system.

C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10  /L:$

Where $ is the drive letter for the CD-ROM drive.  This is where you will 
assign the drive letter to the CD-ROM drive.

If you are using DOS 5.00, the version that MSCDEX.EXE should report 
is 2.21.
If you are using DOS 6.00, the version that MSCDEX.EXE should report 
is 2.22.
If you are using DOS 6.20, the version that MSCDEX.EXE should report 
is 2.23.

If you have run Memmaker and it has put memory locations at the front of 
the Media Vision lines, please remove the memory locations.  Here is a 
sample line that loads the a driver high without the memory location.

DEVICEHIGH=C:\PRO16MM2\MVSOUND.SYS  D:5  Q:10

5.)  If your drive uses a caddy, make sure the caddy lid is closed.  Make 
sure the metal door on the caddy will move smoothly to the left or right, as 
well as return freely to the center.  Try a different caddy.  Make sure the 
CD is not skewed in the drive bay or the CD caddy.  Confirm that the CD 
is not up-side down.  In the drive bay, you can read the label of the CD 
when the drive door is open.  With a caddy, you can see the label of the 
CD through the clear plastic.

Remove the CD from the CD-ROM drive; replace it with a different CD, 
or use a replacement of the original CD.  See if the same error occurs.  If 
there are no more errors, then the first CD was bad.  If it continues with 
the same problem, then something else is wrong.

6.)  Re-seating... Pull the card out of the slot it is currently in and put 
it back in the same slot.  Or, pull the card out of its current slot, 
and put it back into a different slot.

7.)  Reduce your CONFIG.SYS and AUTOEXEC.BAT  files to the bare 
minimums.  You will only want to load MVSOUND.SYS and 
TSLCDR.SYS in the CONFIG.SYS.  In the AUTOEXEC.BAT file, you 
will only want to load MSCDEX.EXE.

If these suggestions do not work, the drive needs to be serviced.

46. I'm getting a "No SCSI host adapter detected" error message.  How do I 
fix this?
1.)  Make sure that the SCSI host adapter is being found when your system 
boots.  Reseat ALL cables and the Sound card.  Try booting the system 
with no SCSI cable attached. You should receive a message from the 
TSLCDR.SYS line that tells you that a SCSI host adapter was detected at 
adress 388h.   If you still receive a "No SCSI host adapter detected," then 
try moving the card to another slot. 

If the SCSI host adapter is detected without the SCSI cable connected, but 
not when it is connected, then you have a bad SCSI cable.  Just replace the 
cable, and everything should fall into place.  Once the host adapter is 
detected, if you still are having problems, please follow the tips below.  

2.) Make sure you have a LASTDRIVE statement in your CONFIG.SYS 
file:

LASTDRIVE=$

Where $ is at least one drive letter BEYOND the last physical drive on the 
system.

3.)  Try the following sample lines in place of your current lines in the 
CONFIG.SYS file.

DEVICE=C:\PRO16MM2\MVSOUND.SYS D:5 Q:11 S:1,220,1,5 M:0 J:1 /W:0
DEVICE=C:\PRO16MM2\TSLCDR.SYS /D:MVCD001 /R

Make sure that these are the last two lines in your CONFIG.SYS file.  
Make sure that TSLCDR.SYS is the very last line in the file.

4.)  You will also want to make sure that you are using the latest version of 
MSCDEX.EXE on your system.  Here is a sample line for your 
AUTOEXEC.BAT file that will ensure that you are using the proper 
version of MSCDEX.EXE for you system.  Make sure that the 
MSCDEX.EXE line in the AUTOEXEC.BAT file is at the TOP of the file.    
Also, assign the drive letter to the CD-ROM drive with the /L:$ parameter.

C:\DOS\MSCDEX.EXE /D:MVCD001 /M:10 /V /L:$

Where $ is the drive letter for the CD-ROM drive.  

If you are using DOS 5.00, the version that MSCDEX.EXE should report 
is 2.21.
If you are using DOS 6.00, the version that MSCDEX.EXE should report 
is 2.22.
If you are using DOS 6.20, the version that MSCDEX.EXE should report 
is 2.23.

47. My third party CD-ROM drive is not working.  What 
gives?
Here are some troubleshooting tips that should get your drive operational.

Make sure you have a LASTDRIVE statement in your CONFIG.SYS file:

LASTDRIVE=$

Where $ is at least one drive letter BEYOND the last physical drive on the 
system.

Try the following sample lines in place of your current lines in the 
CONFIG.SYS file.

DEVICE=C:\PRO16MM2\MVSOUND.SYS D:5 Q:11 S:1,220,1,5 M:0 J:1 /W:0
DEVICE=C:\PRO16MM2\TSLCDR.SYS  /D:MVCD001  /R

Make sure that these are the last two lines in your CONFIG.SYS file.

You will also want to make sure that you are using the latest version of 
MSCDEX.EXE on your system.  Here is a sample line for your 
AUTOEXEC.BAT file that will ensure that you are using the proper 
version of MSCDEX.EXE for you system.  Make sure that the 
MSCDEX.EXE line in the AUTOEXEC.BAT file is at the TOP of the file.  
Also, assign the drive letter to the CD-ROM drive with the /L:$ parameter.

C:\DOS\MSCDEX.EXE /D:MVCD001 /M:10 /V /L:$

Where $ is the drive letter for the CD-ROM drive.  

If you are using DOS 5.00, the version that MSCDEX.EXE should report 
is 2.21.
If you are using DOS 6.00, the version that MSCDEX.EXE should report 
is 2.22.
If you are using DOS 6.20, the version that MSCDEX.EXE should report 
is 2.23.

48. How do I get CD audio from my third party CD-ROM drive?
You will need to contact a company by the name of TTS.  TTS is not 
affiliated with Media Vision.  TTS will be able to provide you with the 
appropriate cables and bracket adapters necessary to connect any CD-
ROM drive to your Pro 16 Multimedia System II.  Here are the 
telephone and fax numbers for TTS.

Voice	800 - 887 - 4968
Voice	408 - 982 - 0653
FAX	408 - 982 - 0738

49. How do I increase the performance of my CD-ROM drive?
Here are some tips on possible ways to increase CD-ROM performance:

1) Increase M-parameter (memory buffers) on MSCDEX.EXE 
(32 is max.)
2) Use /W:0 switch on MVSOUND in CONFIG.SYS.
3) Use Expanded memory , and the /E switch on MSCDEX (only on 
certain computers.)
4) Use /R switch on TSLCDR.SYS (or remove if present.)
5) Use /P3 parameter on TSLCDR.SYS (or remove if present.)  Please 
note that the usage of this parameter with NEC CD-ROM drives is not 
advised.
6) Try use the CD-ROM caching feature contained in SMARTDRV that 
comes with DOS 6.2.  CD-ROM caching is a feature of SMARTDRV
that comes with DOS 6.2.  To ensure that SMARTDRV is caching
your CD-ROM drive, make sure that you do not have the /U switch on
your SMARTDRV line. 

50. What will decrease the performance of my CD-ROM drive?
In general, here are some things that reduce CD-ROM performance:

1) Loading MSCDEX into high memory (most common)
2) Incorrect MSCDEX for your DOS version (common)
3) Using Expanded memory , and the /E switch on MSCDEX (only on 
certain computers)
4) Sound card conflicts (DMA, IRQ, or port address)
5) Loading CD-ROM driver into high memory (uncommon)
6) Have colon on P-parameter on TSLCDR.SYS (i.e. change /P:3  to /P3)
7) Using incorrect version of TSLCDR.SYS.
8) Using the CD-ROM caching that defaults with SMARTDRV that 
comes with MS-DOS 6.2.  To disable the caching feature, add the 
/U switch on your SMARTDRV line.

51. What is Wavetable synthesis?
Wavetable synthesis uses a digital recording samples of real instruments to 
play MIDI music.

52. Is my card wavetable upgradeable?
The PRO 16 MULTIMEDIA SYSTEM II is not a wavetable upgradeable
sound card.  The Premium and Pro 3-D sound cards from Media Vision 
are wavetable upgradeable.

53. What is the KORG wavetable upgrade?  Will it work on my system?
The KORG wavetable upgrade card is a Waveblaster compatible card.  As 
long as your card is Waveblaster compatible, the KORG card will work on 
your system.

54. What are the features of the KORG wavetable 
upgrade card?
  General MIDI compatible
  WaveBlaster compatible feature connector
  32 voice polyphony (simultaneous notes)
  16 part multitimbral (16 instruments at once)
  4Mb of sample ROM containing: 
  	128 musical instruments
  	4 drum set/effects of 47 instruments each
  32 oscillators
  32 dynamic digital low-pass filters
  Onboard DSP provides Reverb and Chorus effects.

55. I am getting "ADLIB is already in use" errors when I try to run my 
DOS applications through Windows.  How do I get rid of this error message?
If you are getting this type of an error, you are loading unnecessary drivers 
when you load Windows.  Check your SYSTEM.INI file for any of the 
following drivers.  If you find any of these, please remark them out with 
semi-colons (;;).  These lines will reside in the [386Enh] section of your 
SYSTEM.INI file.

DEVICE=VADLIBD.386
DEVICE=VSBD.386
DEVICE=VSBPD.386
DEVICE=VSGLX16.386
DEVICE=VSGLD.386
DEVICE=VSGD.386
DEVICE=VSGLX.386

56. I am getting the following error message, "Can't find ver. 2.00 of 
VDMAD.386."
Some Windows applications replace this driver by their own DMA driver.  
To correct this problem, you need to edit your SYSTEM.INI file.  Look in 
the [386Enh] section for the following line:

DEVICE=VDMADX.386

Comment this line out of your file with semi-colons (;;).

;; DEVICE=VDMADX.386

Then, add the following statement to the very beginning of the [386Enh] 
section:

DEVICE=*VDMAD

Restart Windows.  The error message should disappear.

57. Why is Windows making this annoying looping sound when Windows first 
starts?
You are having an IRQ conflict.  You should be able to resolve this quite 
easily.  Please make the following changes to your system files, and you 
should be fine.

CONFIG.SYS

DEVICEHIGH=C:\PRO16MM2\MVSOUND.SYS D:3 Q:12  S:1,220,1,7 M:0 J:1

Test the DMA and IRQ settings by using PLAYFILE under DOS.

Use PLAYFILE under DOS to make sure that we are using a solid DMA 
channel. Make sure that your speakers or headphones are  plugged into the 
OUT jack on the back of the sound card. Please note that you may use 
something other than the TEST.WAV file to test your sound.  Change 
directories to the Media Vision directory (PRO16MM2).  Test the sound by 
entering the following line:


C:\PRO16MM2>PLAYFILE  TEST.WAV	 [enter]

You should hear the .WAV file play once.

If this does not sound normal, adjust the IRQ setting on the 
MVSOUND.SYS line in your CONFIG.SYS file.  Here is a sample line for 
your system.  Once you have sound under DOS, the Windows sound 
should follow.  Make sure that you are using the same DMA and IRQ 
settings under DOS and Windows.  The DMA and IRQ settings for 
Windows can be found in the [mvproaud.drv] section near the bottom of 
the SYSTEM.INI file.

58. I am getting an error message stating that I need to "load Multimedia 
Extensions" before I run the installation program.  How do get rid of this 
message?
Before you can successfully install the Window drivers, you need to edit 
your SYSTEM.INI (in the Windows directory).  Look in the [boot] 
section, and locate a line that looks like this:

DRIVERS=MMSYSTEM.DLL

If this line is gone, add it.  If there is anything else on the end of this 
line, put two semi-colons in front of the whole line.  Here is an example:

;; DRIVERS=MMSYSTEM.DLL POWER.DRV


Add a new line right below the original, and make it look just like the first 
sample line above.  Save the file; re-boot Windows.  Now you can run the 
installation.  After it has completed, remove the new line, and remove the 
semi-colon on the original.

59. MIDI doesn't work on my system.  How do I configure 
the Midimapper?
1) Double-click on Control Panel (in the Main group).
2) Double-click on MIDIMAPPER.
3) Click on NEW.  A dialog box will come up.
4) Enter "Music1" in the name field.
5) Click on OK.  A grid will now come up.
6) In the center column, titled "PORT NAME," click once on [None] to  
bring down a list of available MIDI sound sources.
7) Select "MVI OPL3 FM Synthesizer."  This selection uses the sound 
card to create the MIDI sound for MIDI channel 1.
8) Repeat steps 6 and 7 for MIDI channels 1-10, and 13-16.
9) In the second column, titled "DEST Channel," click once on channel 
16.
10) Using the up and down arrows, change this to 10.  This maps Source 
Channel 16 to Destination Channel 10 (for percussion).
11) Click on OK.  When prompted to save the changes, click on YES.
12) Click on the CLOSE button located near the right of the screen.

60. Ever since I installed your card, Windows locks up when I try to exit.
What is happening?
When exiting Windows, a .WAV file is trying to play.  The sound card is 
not able to play the .WAV file, and at this point, the computer is waiting 
for the file to be played.  It is likely that you are having an IRQ or DMA 
conflict.  Here are some troubleshooting tips that should help you solve this 
problem.  Here is a sample line for your CONFIG.SYS file.

CONFIG.SYS

DEVICE=C:\PRO16MM2\MVSOUND.SYS D:5 Q:11 S:1,220,1,5 M:0J:1 T:1 /W:0

You should first determine that you do not have an IRQ conflict.  You will 
want to test the IRQ values under DOS.  Here is a simple test that will tell 
us whether or not we have a solid IRQ setting.

Reboot the system.  Make sure that your speakers or headphones are 
plugged into the OUT jack on the back of the sound card.  Change 
directories to the Media Vision directory (PRO16MM2).  Test the sound by 
entering the following line:  Please note that you may use something other 
than the TEST.WAV file to test your sound.

PAS  RESET		[enter]
PLAYFILE  TEST.WAV	[enter]

You should hear the sound of a phone dialing.  If you hear no sound, then 
enter the following at the DOS prompt:

DEBUG			[enter]
O A8 05			[enter]
O A9 60			[enter]
Q			[enter]

Try the PLAYFILE command again.  If this now works, download 
SYMPFIX.EXE from the Media Vision BBS, and follow the directions in 
the included text file.

If this does not work, try a different DMA / IRQ combination.  Once there  
is sound in DOS, Windows should also have sound.  If you still have no 
sound  in Windows, then check to make sure that the DMA and IRQ 
settings for Windows match the D: and Q: parameters on the MVSOUND 
line.  You will find the DMA and IRQ settings near the bottom of your 
SYSTEM.INI file for Windows.  Here are the changes that should have 
been made to your SYSTEM.INI.


SYSTEM.INI

[386Enh]
device=vpasd.386
dmabuffersize=064

[mci]
CDAudio=mcicda.drv
mixer=mcimixer.drv

[drivers]
mixer=mvmixer.drv
timer=timer.drv
midimapper=midimap.drv
wave=mvproaud.drv
aux=mvproaud.drv
midi=opl3.drv
midi1=mvproaud.drv

[Multimedia.Setup]
audio=mvproaud.drv,0,0,0

[mvproaud.drv]
dma=x	    (this is the D: value on the MVSOUND.SYS line in the 
CONFIG.SYS)
irq=y	    (this is the Q: value on the MVSOUND.SYS line in the 
CONFIG.SYS)

[opl3.drv]
drumchannel=10


If changing the values for the DMA and IRQ settings do not help, please 
download the following file from the BBS.

GWPATCH.EXE

GWPATCH.EXE is a file that contains a different mix of Windows drivers 
that will often solve Windows lock ups.

GWPATCH.EXE contains the following files:

File: MVMIXER.DRV
Size: 41200
Date: 09-21-93
Time: 2:14p

File: MVPROAUD.DRV
Size: 27344
Date: 08-26-93
Time: 2:31p

File:VPASD.386
Size: 15967
Date: 08-26-93
Time: 2:31p

File: MMMIXER.DLL
Size: 22800
Date: 09-07-93
Time: 9:41a


61. I am getting the error message "can not successfully register the server"
when attempting to access any of the Pocket Tools in Windows. How do I correct
this problem?

The problem can be traced to a corrupted REG.DAT file in the 
WINDOWS directory.

According to the Windows Resource Guide, to restore the database, the 
following must be done:

1. Quit Windows, delete REG.DAT, and then restart Windows.

2. Run Registration Info Editor (REGEDIT.EXE from the Windows 
directory--great icon), which  will display an empty list of registered file 
types.

3. Choose "Merge Registration File" from the File menu.

4. Select "SETUP.REG" (WINDOWS\SYSTEM directory) from the File 
Name list in the dialog box and click the OK button.

This will restore the original Windows Registration Database.

62. Why do all of  my sounds play fast?  It sounds like my card is 
chipmunking.
It is likely that you have a DMA conflict.  Here are some troubleshooting 
tips that should help us figure out what is happening.  Remember that you 
cannot use the same DMA and IRQ for the Pro 16 Multimedia System II
and Sound Blaster emulation portions of the board.

Reboot the system.  Make sure that your speakers or headphones are 
plugged into the OUT jack on the back of the sound card.  Change 
directories to the Media Vision directory (PRO16MM2).  Test the sound by 
entering the following line:  Please note that you may use something other 
than the TEST.WAV file to test your sound.

PAS  RESET			[enter]
PLAYFILE  TEST.WAV		[enter]

You should hear the .WAV file play once in a normal speed.

If this does not sound normal, adjust the DMA setting on the 
MVSOUND.SYS line in your CONFIG.SYS file.  Here is a sample line for 
your system.

DEVICE=C:\PRO16MM2\MVSOUND.SYS  D:3  Q:7  S:1,220,1,5  M:0 T:1

If the sound is fine, please ensure that the DMA you are using under 
Windows matches the DMA you are using under DOS.  Here is a copy of 
what your SYSTEM.INI file should look like as far as Media Vision 
drivers are concerned.  You should notice that the DMA setting is at the 
bottom of your SYSTEM.INI in the [mvproaud.drv] section.

[386Enh]
device=vpasd.386
dmabuffersize=064

[mci]
WaveAudio=mciwave.drv
Sequencer=mciseq.drv
mixer=mcimixer.drv

[drivers]
mixer=mvmixer.drv
timer=timer.drv
midimapper=midimap.drv
wave=mvproaud.drv
aux=mvproaud.drv
midi=opl3.drv
midi1=mvproaud.drv

[Multimedia.Setup]
audio=mvproaud.drv,0,0,0

[mvproaud.drv]
dma=3
irq=7

[opl3.drv]
drumchannel=10

63. Pocket CD won't work.  I am getting the following error message.  "There
is an undetectable problem in loading the specified device driver."
First, make sure that you have a music CD in the drive before and when 
you launch PocketCD.  If not, you will get this error every time.

If you do have a music CD in the drive, and still get the error, you will 
need to:
1) Go to the Control Panel (in Main).
2) Open DRIVERS, and look for [mci] CD Audio.  Double-click on this.
3) If you get a "One CD-ROM found" message, restart Windows, and try 
PocketCD again.  If there is no message, you will need to make sure your 
CD-ROM driver is loading in DOS.

4) You may need to delete and then reinstall the [mci] CD Audio driver.  
This is a Microsoft driver.  Once you have replaced the [mci] CD Audio 
driver and if PocketCD is still not working, you need to exit Windows and 
shut the system down.  Restart your system, and try PocketCD one more 
time.

5.)  Make sure that you are using the proper version of MSCDEX for your 
system. MSCDEX stands for Microsoft CD Extensions.  MSCDEX is a 
DOS version sensitive program.  Here is a sample line for your 
AUTOEXEC.BAT file that will ensure that you are using the proper 
version of MSCDEX.EXE for your system.

C:\DOS\MSCDEX.EXE  /D:MVCD001  /M:10

If you are using DOS 5.00, the version that MSCDEX.EXE should report 
is 2.21.
If you are using DOS 6.00, the version that MSCDEX.EXE should report 
is 2.22.
If you are using DOS 6.20, the version that MSCDEX.EXE should report 
is 2.23.

Finally, update your CD-ROM driver, (if available), since this can also 
create an error with PocketCD.

64. I am unable to use the Media Player in Windows to 
play audio Cds.  How can I correct this problem?
If you do not have an option for CD Audio with Media Player, then you 
will need to edit the MPLAYER.INI file for Windows.  You can use 
Notepad to edit the file.  All you need to do is make sure that you have the 
following line in the [Devices] section.

[Devices]
CDAudio=17,  CD Audio

65. I am only getting sound from one channel when playing a music CD.
The only driver that affects CD Audio is the [mci] CD Audio driver.  This 
is a Windows driver.  It has no affect on the CD-ROM drive under DOS, 
so for trouble shooting purposes, we should find out whether or not you 
are receiving Stereo CD Audio while under DOS.  To test this, you need to 
use the MUSICBOX.EXE  utility.  MUSICBOX should be in your 
PRO16MM2 directory.  Start Musicbox.  Press "P" for Play.  You should 
start hearing CD-Audio.  You can press the <ESC> key to exit the 
program.  The CD-ROM drive will continue to play the disc.  At your DOS 
prompt type the following command.

PAS  RESET	 [enter]

If you now start hearing Stereo sound, then your mixer was out of 
adjustment.

If your drive has a headphones jack, try plugging the speakers or a set of 
headphones into the headphones jack on the CD-ROM drive.  If you still 
do not hear Stereo, then the drive is malfunctioning.

If you hear Stereo out of the headphones jack, then the problem is probably 
with the audio cable itself or its connection to the sound card.  Double 
check all of your connections.  If it is SAFE to operate your PC with the 
cover off, you might try to GENTLY wiggle the audio cable at each end.  
You may just have a bad connection. 

If it can be determined that the audio cable is good, then the sound card is 
going to be the source of the trouble.

If Musicbox works fine, then you should check the Pocket Mixer in 
Windows.  If the Pocket Mixer is set properly, then you should reinstall the 
[mci] CD Audio driver.  You will find the driver in the Drivers Applet 
under Control Panel.  Once you have replaced the [mci] CD Audio driver 
and  if the Windows CD player is still not working properly, you need to 
exit Windows and shut the system down.  Restart your system, and try the 
player one more time.

66. Is there an software developer's kit available for the Pro Audio 
Spectrum 16?
Yes,  please contact the Media Vision Sales department to purchase the 
SDK.  You can reach the Sales Department at 800-845-5870.

67. How do I get TBPRO to work?  It used to work fine, but it doesn't work 
anymore.
Here are some trouble shooting tips that should allow you to use TBPro.  
Please be aware that some of the versions of TBPro that Media Vision 
ships is an 8 bit version.

1.)  Use an 8 bit DMA.  Here are some sample lines for your 
CONFIG.SYS and AUTOEXEC.BAT files.

CONFIG.SYS

DEVICE=C:\PRO16MM2\MVSOUND.SYS  D:3  Q:5  S:1,220,1,7  M:0 J:1

AUTOEXEC.BAT

SET BLASTER=A220  D1  I7  T3

2.)  Use TBCONFIG.EXE to reconfigure TBPro.  Try reducing the 
sampling rate.  You might also try turning the Graphics mode OFF.

3.)  There is an updated version of TBPro on the BBS.  This version 
supports the usage of 16 bit DMA's.  The filename is TBPRO.EXE

68. Can I connect other SCSI devices to the Pro Audio 
Spectrum?
Yes.  You need to purchase an ASPI driver from Adaptec.  You can call 
the Adaptec Software Hotline at 1-(800)-442-SCSI , and request pricing 
information on a product called SCSIworks!.   International customers will 
need to call (408)-945-8600 and ask for Pre-Sales.  You can also fax in 
your requests to:

(716)-873-0906
"Attn: Adaptec Order Desk"

After you install the correct driver from this product, you will have access 
to your SCSI device through the SCSI host adapter on the sound card.
SCSIworks! supports SCSI hard drives, scanners, tape backup units, and 
many other SCSI devices.

69. I am getting the following error message when I use RECFILE.  "File is full
or blocked."I am also not able to record 16 bit files.  What is happening here?
This problem is caused by slow system throughput.  To correct this,please 
try the following:

1.)  Reduce to a generic CONFIG.SYS and AUTOEXEC.BAT.

2.)  Make sure that your hard disk has been optimized (defragmented).  If 
you are using some kind of compression, like stacker, then it is very likely 
that you will not be able to record at the higher levels like 44khz because it 
uses so much disk space, you'll need something like 10 megs of 
unfragmented disk space, stacker causes the disk to be fragmented, so 
RECFILE won't work with the higher settings.

3.)  Try a lower sampling rate or try recording to a ramdrive.

70. Why am I getting a GPF (General Protection Fault) in "user.exe" when I
try to use Pocket Recorder?
If you are unable to record, you may have to "reset" the Pocket Recorder 
section of your WIN.INI file before the Pocket Recorder will start working 
again.  Here is how you would "reset" the section.

1.)  Edit the WIN.INI file.

2.)  Find the section labeled:  [Media Vision Pocket Recorder]

3.)  Highlight (select) the entire section with your mouse.  Make sure that 
you ONLY select the [Media Vision Pocket Recorder] section.

4.)  Press the DELETE key.  This will remove the entire section.  

5.)  Save the WIN.INI.

6.)  Exit Windows.

7.)  Restart Windows.  Try the Pocket Recorder.

